Pull Request Description

The delay until data is propagated and endpoints don't return wearable that is transferred to another user is handled properly.
Wearable will still show in the grid (endpoint returns it) but it will be detected that is being transferred and it will prevent wearable to be chosen and equipped. Check the screenshot how it looks.

In addition these things are added:

• counter for wearables/emotes in the grid (same style as in gifting popup)
• outfits that contain wearables that are being transferred are ignored, slot will appear empty (the same happens on backend, when data is propagated fully and backend ignores this outfit automatically)

What does this PR change?

Solves #5901

Test Instructions

Two users, lots of wearables/emotes

Test Steps

1. From user A transfer wearable/emote to User B and wait for success confirmation
2. Observe that wearable/emote is greyed out and message appears that wearable is being transferred) on user A
3. Observe that count was decreased (if user had multiple items)

NOTE: there is a edge case that I think will happen rarely but possible in testing:

• User A sends to User B
• on User A writes that transfer is pending
• User A closes client
• User B sends the same wearable to User A
• User A opens the client and thinks that he is still transferring the wearable

we can create a new ticket for this, we can add timestamps or something like that to solve it

Additional Testing Notes

• Note any edge cases to verify
• Mention specific areas that need careful testing
• List known limitations or potential issues

Quality Checklist

• Changes have been tested locally
• Documentation has been updated (if required)
• Performance impact has been considered
• For SDK features: Test scene is included

Code Review Reference

Please review our Code Review Standards before submitting.